<?php
session_start();
?>


<?php

$id = $_REQUEST['id'];
$_SESSION['id'] = $id;

?>

<html>
	<head>
		<title></title>
	</head>
	<body bgcolor="AliceBlue">
	
	<form  method="post" action="processDesignNote.php">
		<table border="1" cellpadding="1" cellspacing="1" style="width: 500px;">
			<thead>
				<tr>
					<th scope="col">
						Design Note</th>
					<th scope="col">
						Description</th>
					<th scope="col">
						response</th>
				</tr>
			</thead>
			<tbody>
				<tr>
					<td>
						section 1 : Design Requirement.</td>
					<td>
						Clearly understand the scope of the activity.</td>
					<td>
						<input type="text" name="response1" id="response1"/></td>
				</tr>
				<tr>
					<td>
						<table border="0" cellspacing="0" cols="1" frame="VOID" rules="NONE">
							<colgroup>
								<col width="329" />
							</colgroup>
							<tbody>
								<tr>
									<td align="LEFT" height="34" width="329">
										section 2: Design Description and Analysis</td>
								</tr>
							</tbody>
						</table>
					</td>
					<td>
						Clearly mention what are you fixing and analysis done as a part of this activity. Are you really fixing the root cause of the problem.</td>
					<td>
						<input type="text" name="response2"  id="response2"/></td>
				</tr>
				<tr>
					<td>
						section 3 : Design Options</td>
					<td>
						Discuss various design options with their pros and cons. Each design option must have effort (implementation &amp; testing), LOC, complexity, performance impact (CPU, memory, link usage etc), extensibility, maintainability and modularity aspects. Rational behind choosing one design option over others.</td>
					<td>
						<input type="text" name="response3"  id="response3"/></td>
				</tr>
				<tr>
					<td>
						section 4 : static model.</td>
					<td>
						If we are adding structures or data members in classes , it will be helpful if we provide class model so that reviewers can brainstorm if it is the best place to change or not.</td>
					<td>
						<input type="text" name="response4"  id="response4"/></td>
				</tr>
				<tr>
					<td>
						section 5 : Dynamic model.</td>
					<td>
						Add sequence diagram to explain how your design changes effecting the existing functionality or different scenarios. It will help in analyzing impact of code in much better way.</td>
					<td>
						<input type="text" name="response5"  id="response5"/></td>
				</tr>
				<tr>
					<td>
						section 6 : Testing scope and Strategy</td>
					<td>
						Are you really understanding the interactions and incorporating test coverage as a part of test strategy. It will help in identifying if any effected domain is missed in testing.</td>
					<td>
						<input type="text" name="response6"  id="response6"/></td>
				</tr>
			</tbody>
		</table>
		<p>
			<input name="submit" type="submit" value="Proceed" /><input name="reset" type="reset" value="Reset" /></p>
			
			</form>
	</body>
</html>
